Summary

Next.js uses an exception-based mechanism to determine whether a route is dynamic. For instance, when cookies or headers are accessed within a static route, a DynamicServerError is triggered, which disables static generation for that route.

However, since this error is currently being caught for error reporting purposes, Next.js fails to detect dynamic hook usage correctly, resulting in a build failure.

This PR addresses the issue by allowing these errors to propagate up the call stack, enabling accurate detection of dynamic hooks and ensuring the build process succeeds.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings